I don't object to these changes, but I'm curious. What is the point of treating | as | inside a string?

In the implementation, it seems better to handle it in the case just just above the one your modified that handles \ and " similarly. Please add a LOG entry and a couple of mats.

@dybvig I'll rewrite the patch accordingly.
It seems the only reason | is included is for compatibility with '|foo|bar|. Not a decision I know how to defend myself, but it is what r7rs is ;)

When asking on #scheme (2018-06-22), the answer was:
\| is necessary when escaping symbols, and we allowed it in strings for uniformity

Recognizing that this a relatively small change, it should probably update the documentation to reflect the added character names and string escape. The LOG entries should also include the modified file, as the other entries in the LOG do.

May I help with something if it is stalled?

@ecraven, if you'd like to proceed with this change, please update the documentation and release notes.